-
Notifications
You must be signed in to change notification settings - Fork 81
refactor: remove note screener API #1630
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
e800bdb to
d7795cb
Compare
| /// Returns the block number at which the note can be consumed. | ||
| /// Returns None if the note is already consumable or never possible | ||
| #[wasm_bindgen(js_name = "consumableAfterBlock")] | ||
| pub fn consumable_after_block(&self) -> Option<u32> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should return BlockNumber here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be wrong, but I think that we are using u32 to send block numbers in the web client, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I don't think there is a BlockNumber JS model struct. Maybe we can add one but it doesn't seem too critical.
fkrause98
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good, should we also add tests for the web client exposed models?
Blocked: depends on a
miden-basedep withCloses #1381